ci: Don't create python releases as drafts#2950
Merged
Conversation
This partially reverts commit 7890e2f.
cqc-alec
approved these changes
Mar 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This partially reverts #2892.
The idea of that PR was to create the python releases as Draft while wheels are being built, only to mark them as ready once the wheels have been submitted.
Turns out, creating a draft release not only does not trigger
releaseworkflows but also it doesn't create tags 🫠So here instead we are creating a non-draft release, and marking it as draft when the wheels building workflow start.
This won't help when we want to start using github's new immutable releases, but at least mimics the behaviour for now.
(Ideally we'd just create a tag plus the draft release, but we don't have control over
release-please's behaviour there).